IBM Books

Nways Multiprotocol Access Services Software User's Guide Version 3.3


The CONFIG Process (CONFIG - Talk 6) and Commands

This chapter describes the CONFIG process configuration and operational commands. It includes the following sections:


What is CONFIG?

The Configuration process (CONFIG) is a second-level process of the device user interface. Using CONFIG commands, you can:

Note:Refer to the chapter "Migrating to a New Code Level" in 2216 Nways Multiaccess Connector Service and Maintenance Manual for information about migrating to a new code level.

CONFIG lets you display or change the configuration information stored in the device's nonvolatile configuration memory. Changes to system and protocol parameters do not take effect until you reload the device software. (For more information, refer to the OPCON reload command in "What is the OPCON Process?").
Note:You must enter the write command to save the changes in the device's flash memory.

The CONFIG command interface is made up of levels that are called modes. Each mode has its own prompt. For example, the prompt for the SNMP protocol is SNMP config>.

If you want to know the process and mode you are communicating with, press Enter to display the prompt. Some commands in this chapter, such as the network and protocol commands, allow you to access and exit the various levels in CONFIG. See Table 7 for a list of the commands you can issue from the CONFIG process.

Config-Only Mode

Config-Only mode is entered if the configuration file that you are using is empty or no protocols are configured. Config-Only mode can also be entered manually to recover from an invalid configuration that is causing the router to crash during start-up.

Automatic Entry Into Config-Only Mode

Config-Only mode is entered if the router is booting with an empty configuration file or the configuration file contains incomplete configuration data.

The following conditions cause the router to enter Config-Only mode:

Manual Entry Into Config-Only Mode

To enter Config-Only mode, do one of the following:

See "Accessing the Firmware from the Command Line Interface" for more information.

Quick Configuration

Quick Configuration (Quick Config) provides a minimal set of commands that allow you to configure bridging protocols and routing protocols present in the router load. You can also configure an SNMP community with WRITE_READ_TRAP access. This is useful during initial setup because the configuration program uses SNMP SET commands to transfer the configuration.
Important:At least one network device must be configured before using quick config. To add a device, use the add device command at the config(only)> or config> prompt. See Accessing the Network Interface Configuration Process for more information.

The following table lists the protocols supported by Quick Config.

Table 6. Quick Config Capabilities
ATM Protocols Bridging Protocols Routing Protocols
LAN Emulation STB, SRT, SRB IP, IPX, DNA IV

Quick Config complements the existing configuration process by offering a shortcut. This shortcut allows you to configure the minimum number of parameters for these bridging protocols and routing protocols without having to exit and enter the different configuration processes. The other parameters are set to selected defaults.

Situations that call for the router to be quickly configured are:

Quick Config operates as follows:

Quick Config sets a number of default parameters based upon how you answer the configuration questions. What cannot be configured with Quick Config can be configured using Config after exiting Quick Config.

You cannot delete Quick Config information from within Quick Config. However, you can correct information either by exiting and returning to Quick Config, or by entering the reload command as a response to some Quick Config questions.

For complete information on using the Quick Config software, see Appendix A, "Quick Configuration Reference".

Manual Entry Into Quick Config Mode

You might want to run Quick Config manually to demonstrate the router's capabilities or to reconfigure dynamically to perform benchmark tests without having to learn the router's operating system commands.

To enter Quick Config, type qconfig at the Config> prompt.

Exiting from Quick Config Mode

To exit Quick Config, restart by entering r from any prompt. Follow the queries until you enter no and then enter q to quit. The router returns to either the Config (only)> or the Config> prompt.

Configuring User Access

The device configuration process allows for a maximum of 50 user names, passwords, and levels of permission. Each user needs to be assigned a password and level of permission. There are three levels of permission: Administration, Operation, and Monitoring.

For more information, see ***.

Technical Support Access

If you are the system administrator, when you add a new user for the first time, you are asked if you want to add Technical Support access. If you answer yes, Technical Support is granted the same access privileges that you have as system administrator.

The password for this account is automatically selected by the software and is known by your service representative. This password can be changed using the change user command; however, if you do change the password, customer service cannot provide remote support. For additional information on the use of the change user command, see "Change".

Configuring Spare Interfaces

Occasionally, you may need to configure a new interface along with its bridging and routing protocols without having to restart the device. You can accomplish this by configuring a number of spare interfaces on your device. Spare interfaces are useful if:

To configure a spare interface:

  1. Access the CONFIG process by entering configuration.

  2. Configure the number of spare interfaces for the device using the set spare-interfaces command.

  3. Exit the CONFIG process by pressing Ctrl-P.

  4. Reload the device.
Example:
* configuration
Config> set spare 2
Config>
*reload
Are you sure you want to reload the gateway? (Yes or [No]) yes

When the device reloads, the spare interfaces are installed as null devices.

To use one of the spare interfaces:

  1. Insert the new adapter into the adapter slot.
    Note:If you are using an ESCON or Parallel channel adapter, you have the ability to define spare interfaces for each of the attached networks without using additional adapters. In this case, you can bypass this step.

  2. Access the CONFIG process by entering configuration.

  3. Add an interface or a dial circuit using the add device command, if necessary.

  4. Configure the spare interface by using the net command to configure the interface or add ATM LAN Emulation clients.

  5. Configure the various protocols and features using the protocol and feature commands.

  6. Exit the CONFIG process by pressing Ctrl-P.

  7. Access the GWCON process by entering console.

  8. Bring the new interface online to the network using the activate command.

The following example shows how to configure and activate a new dial circuit on which the IP protocol is enabled. The dial circuit and IP protocol configuration are not shown.

Example:

*configuration
Config> add device dial-circuit
Config> net 6
Circuit configuration
Circuit config>
 · Here you would configure the dial circuit
 
 ·
Circuit config> exit
Config> protocol ip
IP>
 
 · Here you would configure the IP protocol on the dial circuit.
 
·
IP> exit
Config>
*console
+activate 6

The following example shows how to configure and activate a new ATM LAN Emulation Client on which the IP protocol is configured. The ATM LAN Emulation Client and IP configurations are not shown.

* configuration
Config> net 0
ATM User Configuration
ATM Config> le-client 
ATM LAN Emulation Clients Configuration
LE Client config> add token-ring 
Added Emulated LAN as interface 6
LE Client config> config 6
ATM LAN Emulation Client configuration
·
(Here you would configure the ATM LAN Emulation Client)
·
Token Ring Forum Compliant LEC Config> exit
LE Client config> exit
ATM Config> exit
Config> protocol ip
IP Conifg>
·
(Here you would configure IP on the ATM LAN Emulation Client)
·
IP Config> exit
Config> write
ctrl-p
* console
+ activate 6
Interface 6 activated successfully

Restrictions for Spare Interfaces

The activate command cannot be used to activate a new interface on the network under the following conditions:

In these cases, you must restart the device to bring the new interface online.

You can configure the following interfaces as spare interfaces, but you cannot activate them on the network using the activate command:

You must restart the device to bring these interfaces online.

You can configure the following protocols on spare interfaces, but you cannot activate them on the network using the activate command:

Note:When using the configuration program, use the following to work with spare interfaces:

  1. Make the configuration changes for the spare interface on the device

  2. Enter the activate command on the device to bring the spare interface, protocols, and features online

  3. Retrieve the configuration using the configuration program

  4. Save the retrieved configuration into the configuration program database

There are requirements for certain functions. These are:
APPN To activate this protocol on a spare interface, you must first activate the interface and then configure the protocol on the activated interface.
   
Bandwidth Reservation (BRS) To configure BRS on a spare interface, you must enable BRS on each network interface where Frame Relay circuits will be active before activating the spare interface. After activating the spare interface, you can then use BRS configuration commands to make changes such as adding a traffic class or assigning a protocol to a traffic class.
   
DECnet IV To activate this protocol on a spare interface, you must first activate the interface and then configure the protocol on the activated interface. Use the DECnet IV set command to activate the configuration changes.
   
Frame Relay

  • You cannot activate an FR dial circuit interface unless the dial circuit's base net is already active.

  • An activate for an FR dial circuit will fail if the frame size, MAC header, or trailer required by the spare interface is larger than other dial circuits already assigned to the base net.

  • If data compression is not already active in the device, data compression will not work on a spare interface defined for data compression.

   
BGP Use the BGP reset neighbor command to activate new neighbors. 
IPX Use the reset command to activate static routes, static services, and filter lists on the spare interface.
   
PPP

  • If data compression is not already active in the device, data compression does not work on a spare interface defined for data compression.

  • You cannot activate a spare PPP interface if the device's global buffer is too small to support a 1500-byte PPP MRU.

  • You cannot activate a PPP dial circuit interface unless the dial circuit's base net is already active.

  • An activate for a PPP dial circuit will fail if the frame size, MAC header, or trailer required by the spare interface is larger than other dial circuits already assigned to the base net.

   
Bridging

  • Bridging was not already active.

  • NetBIOS filters are defined on the spare interface.

  • The spare interface caused a change to the bridge personality or behavior (for example, adding SR port to pure TB bridge.

   
IP Use the reset IP command to bring configuration changes online for access-controls and packet-filters.
   
Channel Virtual Nets (MPC, LCS, LSA) The spare interface cannot be activated if its configured subchannels are already in use by or shared with another interface.
   
WAN Restoral/ WAN Reroute The spare interface cannot be activated if any of the following conditions exist:

  • The spare interface is configured as a WRS primary, and its configured WRS secondary is already a WRS primary or WRR primary or WRR alternate.

  • The spare interface is configured as a WRS primary, and its configured WRS secondary is already actively restoring some other WRS primary.

  • The spare interface is configured as a WRS secondary, and its configured WRS primary is already a WRS secondary or WRR primary or WRR alternate.

  • The spare interface is configured as a WRS secondary, and its configured WRS primary is already actively being restored by some other WRS secondary.

  • The spare interface is configured as a WRR primary, and its configured WRR alternate is already a WRS primary or WRS secondary or WRR primary or WRR alternate.

  • The spare interface is configured as a WRR alternate, and its configured WRR primary is already a WRS primary or WRS secondary or WRR alternate.

  • The spare interface is configured as a WRR alternate, and its configured WRR primary is already actively being rerouted by some other WRR alternate.

Resetting Interfaces

Occasionally, you might need to change the configuration of a network interface along with its bridging and routing protocols without restarting the device. The reset command allows you to disable a network interface and then enable it using new interface, bridging and routing configuration parameters.

The interface, protocols and features configuration parameters are changed using the CONFIG process (talk 6) commands. The talk 6 commands affect the contents of the configuration memory. The configuration changes are activated by issuing the GWCON process (talk 5) reset command.

To reset an interface:

  1. Access the CONFIG process (talk 6).

  2. Use the net command and other commands to change configuration parameters.

  3. Use the protocol and feature commands to change the interface-based configuration parameters.

  4. Exit the CONFIG process by pressing Ctrl-P.

  5. Access the GWCON process (talk 5).

  6. Use the reset command to reset the interface and the protocols and features on the interface.

Example:

           * configuration
           Config>net 1
           PPP Config>
 
           . . . change PPP parameters . . .
 
           PPP Config>exit
           Config>protocol ipx
           IPX Config>
 
           . . . change IPX parameters on the PPP interface . . .
 
           IPX Config>exit
           Config>
           *talk 5
           +reset 1
           Resetting net 1 PPP/0...successful
Note:When using the configuration program, do the following to make configuration changes to existing interfaces:

  1. Make the configuration changes for the interface on the device

  2. Enter the reset command to reset interface, protocol and feature parameters

  3. Retrieve the configuration using the configuration program

  4. Save the retrieved configuration into the configuration program database

Restrictions for Resetting Interfaces

The reset command cannot be used to reset a network interface if:

In these situations, you must reload the device to activate the configuration changes.

You can change the configuration parameters of the following types of interfaces, but you cannot activate the changes using the reset command:

You must reload the device to activate the configuration changes.

You can change the configuration parameters of the following protocols and features, but you cannot activate the changes using the reset command:

You must reload the device to activate the configuration changes.

There are also requirements for certain functions. They are:
PPP dial circuits A PPP dial circuit cannot be reset if any of the dial circuit parameters have changed.
   
Frame Relay dial circuits A Frame Relay dial circuit cannot be reset if any of the dial circuit parameters have changed.
   
Compression Compression requires large header and trailer sizes. Unless compression is already enabled on some other interface, it is likely that the header and trailer sizes will be too small. In this case, compression is disabled automatically on the interface and an ELS message is logged (rather than causing the entire reset interface to fail).
   
ESCON base net Resetting the ESCON base net automatically resets all associated virtual nets.
   
PCA base net Resetting the PCA base net automatically resets all associated virtual nets.
   
Channel virtual nets (MPC,LCS, LSA) Must reset the ESCON or PCA base net in order to reset the following virtual net parameters: Subchannels (adding/deleting/changing/moving), LAN type, LAN number, Block timer, Acknowledgement length.
   
Bridging

  • Bridging was not already active.

  • NetBIOS filters are defined on the interface you are resetting.

  • The reset interface caused a change to the bridge personality or behavior (for example, adding SR port to pure TB bridge.

   
BGP Use the BGP reset neighbor command to activate neighbor configuration changes.
   
APPN Use the activate_new_config command to activate configuration changes.
   
IPX Use the IPX reset command to activate configuration changes for static routes, static services, and filter-lists.
   
DNA IV Use the DNA IV set command to activate configuration changes.
   
SNMP Use the SNMP revert command to activate configuration changes.

Using System Dumps

A useful tool for debugging problems with the 2216 is the system dump. The dump is a compressed snapshot that the system saves to the hard drive if one is present, or to a remote host on the network .

To configure dumping:

  1. Specify which three dump files you will save. See page *** for more information.
  2. Specify whether you want dumping re-enabled after a dump occurs. See page *** for more information.
  3. Enable dumping on the 2216. See page *** for more information.

You can view the status of system dumping or retrieve a dump from the system. See "System View" and System Retrieve, respectively.


Entering and Exiting CONFIG

To enter the CONFIG process from OPCON and obtain the CONFIG prompt, enter the configuration command. Alternatively, you can enter the OPCON talk command and the PID for CONFIG. The PID for CONFIG is 6.

* configuration

or

* talk 6

The console displays the CONFIG prompt (Config>). If the prompt does not appear, press the Enter key again.

To exit CONFIG and return to the OPCON prompt (*), enter the intercept character. (The default is Ctrl-P .)


CONFIG Commands

This section describes each of the CONFIG commands. Each command includes a description, syntax requirements, and an example. The CONFIG commands are summarized in Table 7.

After accessing the CONFIG environment, enter the configuration commands at the Config> prompt.

Table 7. CONFIG Command Summary
Command Function
? (Help) Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help".
 Add   Adds an interface to the device configuration, or a user to the device. 
 Boot   Enters Boot CONFIG command mode. 
 Change   Changes a user's password or a user's parameter values associated with this interface. Also changes a slot/port of an interface. 
 Clear   Clears configuration information.  
 Delete   Deletes an interface from the router configuration or deletes a configured user.  Also deletes system dump files.
 Disable   Disables command completion, login from a remote console, disables modem use  
 Enable   Enables command completion, login from a remote console, enables modem use  
 Event   Enters the Event Logging System configuration environment. 
 Feature   Provides access to configuration commands for independent device features outside the usual protocol and network interface configuration processes. 
 List   Displays system parameters, hardware configuration, a complete user  list.
Load Lists, adds, or deletes optional software packages.
 Network   Enters the configuration environment of the specified network. 
 Patch   Modifies the device's global configuration. 
 Performance   Provides a snapshot of the main processor utilization statistics. 
 Protocol   Enters the command environment of the specified protocol. 
 Qconfig   Initiates the Quick Config process. 
 Set  Sets system-wide parameters for buffers, host name, inactivity timer, packet size, prompt level, number of spare interfaces, dump parameters, location, and contact person.
System Retreive Retrieves dumps
System View Displays the dump settings and the current dump status. Also displays a summary of the dumps.
 Time   Keeps track of system time and displays it on the console. 
 Unpatch   Restores patch variables to default values. 
 Write   Writes the current configuration information to the nonvolatile memory. 

Add

Use the add command to add an interface to the configuration, or user-access.

This command also recreates device records if the configuration is inadvertently lost.

Syntax:

add
callback . . .

device

isdn-address . . .

ppp-user

tunnel-profile

user . . .

v25-bis-address

callback
Use the add callback command to add, delete, or list information for callback on ISDN.

Add
Adds a callback number to the authentication lists.

Delete
Deletes a callback number from the authentication list.

Lists
Displays the authentication list and other related information.

device device_type additional-config-info
With the add device command, you must enter the interface device type (device_type). You are prompted for additional configuration parameters. This additional information varies by device and platform. Refer to "Adding Devices" for additional information about device type and configuration parameters.
Note:If you are adding more than one interface, the order in which you add them is important because the device assigns a sequential interface number to the device when it is added. This interface number is an index number in the device list; it links the device with other protocol configuration information, such as the IP addresses associated with the device. (For more information, refer to the list devices command, "List".)

All device and protocol configuration information related to network interfaces is stored by interface number. Any changes made to interface numbers will invalidate much of the device configuration information in the protocols.

Example:

add device atm
Device Slot #(1-8) [1]? 2
Adding CHARM ATM Adapter device in slot 2 port 1 as interface x
(where x is the interface number assigned)

To determine which devices you can add, use the add devices ? command.

isdn-address address-name network-dial-address network-subdial-address
Adds the local and remote numbers of the ISDN end-points that will be communicating with your router.

address-name
Can be anything (such as a description of the port).

network-dial-address
The telephone number of the local or the destination port.

network-subdial-address
The additional part of the telephone number, such as an extension, that gets interpreted when the interface connects to a PBX; this parameter is optional.
Note:You can use punctuation, such as parentheses and dashes, but the punctuation is not significant (the router uses only the numbers).
Example: add isdn-address line 1 local
Assign network dial address [0 - 32 digits]? 1 2345 67
Assign network subdial address [0 - 19 digits]? 98765

ppp-user
Adds the user profile of a remote user to the local PPP user data base. You can add up to 500 users. You add a PPP user for each remote router or DIALs client that can connect to the device you are configuring. You must configure PPP users if either of the following conditions exist:

If ECP has been enabled for the user, you are prompted for the PPP user name, password, IP address, and encryption key .

If the DIALs feature is in the software load, you are asked if this is a DIALs user.

If you are adding a user for a DIALs client, then you are prompted for the hostname, type of route, network mask, connect time, and call-back information.

See "Using a Dial-In Access to LANs (DIALs) Server" in the Using and Configuring Features for more information.

A user profile stored locally on the device consists of the following:

Name
The userid of the PPP user, used during authentication. See "PPP Authentication Protocols".

Password
The password known to the user and the device, used during authentication. It can be up to 31 characters in length, consist of any alphanumeric character, and is case sensitive. See "PPP Authentication Protocols" for more information.

Enter again to verify
Enter the password again for verification.

Allow inbound access
Allows inbound access to this user profile.

Valid values: yes, no

Default value: no

Will user be tunneled?
Specifies whether this dial-in user should be tunneled to an LNS destination. If you enter "yes", you are prompted for information about the LNS.

Valid values: yes, no

Default value: no

Number of days before account expiry
The number of days before the account expires.

Valid values: 0 to 360

Default value: 180

Number of grace logins allowed
The number of login attempts allowed after the password expires.

Valid values: 0 to 100

Default value: 0

Hostname to use when connecting to this peer:
Specifies the local hostname of this LAC that is passed as identification to the LNS during tunnel setup.

Tunnel Server endpoint:
Specifies the IP address of the LNS to which this user is tunneled.

Type of Route
Either "Host Route" or "Net Route."

A host route is generally applied for single-user access. A net route is generally applied to a network access. A net route allows you to enter a net mask.

IP Address
IP address to be assigned to a user.

A user profile-based IP address to offer to a dial-in client if requested. There are a number of ways for a 2216 to obtain an IP address for a dial-in client. See "IP Control Protocol" for more information.

Valid values: any valid IP address

Default value: none

Net-Route Mask
Mask for a network user.

If the dial-in user is connecting to a DIALs-enabled PPP interface, the router automatically adds a temporary static route to that client for the duration of the PPP session. Typically, this static route has a net mask of 255.255.255.255 (the default value), which implies that there is a single IP host at the other end of the PPP link. However, the net mask can be overridden. If configured, this mask is used when adding the temporary route. An example of this is a small router with a single network of hosts that dials into a DIALs-enabled router. The single route to the small office router will be installed automatically based on the user profile, making it unnecessary to configure routing protocols between the two hosts and cutting down on routing traffic overhead over a potentially slow link.

Hostname
Hostname to be sent to the Proxy DHCP server for use by Dynamic DNS. See "Using a Dial-In Access to LANs (DIALs) Server" in Using and Configuring Features for more information.

Time-Allotted
The length of time a DIALs user can be connected. This is the total for this session, and should not be confused with an inactivity timer.

Valid Values: 0 to 71 827 788 minutes (0=unlimited)

Default Value: 0

Callback type
Call-back method, either "Roaming" or "Required." The call-back parameters are used to specify whether the router will call back the user and what number to call back. See "Configuring PPP Callback" for additional information.

Set encryption key
Specifies whether ECP encryption is to be enabled for this user/port.

Valid values: yes, no

Default value: no

ECP encryption key
Enter 16-character ECP encryption key.

This parameter is displayed only if PPP Encryption Control Protocol (ECP) has been enabled using the talk 6 PPP Config> enable ecp command. MPPE does not require an encryption key. This ECP encryption key is used by the PPP Encryption Control Protocol (ECP). See "Using and Configuring Encryption Protocols" in Using and Configuring Features.

Disable user
Allows you to disable a user-profile.

Valid values: yes, no

Default value: no

Example:

Config> add ppp-user
Enter name:  [ ]? pppusr01
Password:
Enter again to verify: 
Allow inbound access for user? (Yes, No): [yes] 
Will user be tunneled? (Yes, No): [No] 
Number of days before account expiry[0-1000] [0]? 10
Number of grace logins allowed after an expiry[0-100] [0]? 5
IP address: [0.0.0.0]? 1.1.1.1
Set ECP encryption key for this user? (Yes, No): [No] no
Disable user ? (Yes, No): [No]
 
     PPP user name: pppusr01
   User IP address: 1.1.1.1 
      Virtual Conn: disabled
        Encryption: disabled
            Status: enabled
    Login Attempts: 0
    Login Failures: 0
  Lockout Attempts: 0
   Account expires: Sun 17Feb2036 06:28:16
  Account duration: 10 days  00.00.00
   Password Expiry: <unlimited>
 
User 'pppusr01' has been added
 

Example:

Config> add ppp-user
Enter name:  [ ]? tunusr01
Password:
Enter again to verify: 
Allow inbound access for user? (Yes, No): [yes] 
Will user be tunneled? (Yes, No): [No] yes
Enter hostname to use when connection to this peer: []? host01
Tunnel-Server endpoint address: [0.0.0.0]? 1.1.1.1
 
--more--           PPP user name: tunusr01
--more--                Endpoint: 1.1.1.1
--more--                Hostname: host01
 
User 'tunusr01' has been added
 
 

Example with ECP encryption:

Config>add ppp-user
Enter name:  [ ]? ppp_user2
Password:
Enter again to verify:
Allow inbound access for user? (Yes, No): [Yes]
Will user be tunneled? (Yes, No): [No]
Is this a 'DIALs' user? (Yes, No): [Yes]
Type of route?  (hostroute, netroute): [hostroute]
Number of days before account expiry[0-1000] [0]?
Number of grace logins allowed after an expiry[0-100] [0]?
IP address: [11.0.0.185]?
Allow virtual connections? (Yes, No): [No]
Give user default time allotted ? (Yes, No): [Yes]
Enable callback for user? (Yes, No): [No]
Will user be able to dial-out ? (Yes, No): [No]
Set ECP encryption key for this user? (Yes, No): [No] y
Encryption key should be 16 characters long.
Encryption Key (16 characters ) in Hex(0-9, a-f, A-F):
Encryption Key again (16 characters) in Hex(0-9, a-f, A-F):
ECP encryption key is set.
Disable user ? (Yes, No): [No]
 
 
     PPP user name: ppp_user2
   User IP address: 11.0.0.185
     Netroute Mask: 255.255.255.255
          Hostname:       Virtual Conn: disabled
      Time alotted: Box Default                                                
           Callback type: disabled
          Dial-out: disabled
        Encryption: enabled
            Status: enabled
    Login Attempts: 0
    Login Failures: 0
  Lockout Attempts: 0
    Account Expiry:    Password Expiry: 
Is information correct? (Yes, No, Quit): [Yes]
 
User 'ppp_user1' has been added            

tunnel tunnel-name
Gives a tunnel peer access through an IP network to the router. The peer is then authorized to initiate tunneled PPP sessions into the router. To configure a tunnel you must specify:

Name
The hostname of the tunnel peer.

Hostname to use when connecting to this peer
The local hostname to use when connecting to this peer. This name is used for identification of the host on the peer.

Set shared secret
Specifies whether a shared secret is to be used.

Shared Secret
The secret shared between the LAC and LNS. It must be exactly the same on both ends of the tunnel.

Enter again to verify
Enter the shared secret again for verification.

Tunnel-Server endpoint address
The IP address of the tunnel peer (LAC or LNS).

Example:

Config> add tunnel
Enter name:  []? tunnel02
Enter hostname to use when connecting to this peer: []? host02
Set shared secret? (Yes, No): [No]? yes
Shared secret for tunnel authentication:
Enter again to verify:
Tunnel-Server endpoint address: [0.0.0.0]? 2.2.2.22
 
       Tunnel name: tunnel02
          Endpoint: 2.2.2.22
 

user user_name
Gives a user access to the device. You can authorize up to 50 users to access the device. Each user_name is eight characters and is case-sensitive.

When the first user is added, console login is automatically enabled. Each user added must be assigned one of the permission levels defined in Table 8.

When users are added, set login authentication to local. Otherwise a remote server must be used.

Table 8. Access Permission
Permission Level Description
Administrator (A) Displays configuration and user information, adds/modifies/deletes configuration and user information. The Administrator can access any router function.
Operator (O) Views router configuration, views statistics, runs potentially disruptive tests, dynamically changes router operation, and restarts the router. Operators cannot modify the permanent router configuration. All actions can be undone with a system restart.
Monitor (M) Views router configuration and statistics but cannot modify or disrupt the operation of the router.
Tech Support Allows your service representative to gain access to the router if a password is forgotten. Cannot be assigned to users.
Note: To add a user, you must have administrative permission. You do not have to reinitialize the router after adding a user.

Example:

add user John
Enter password:
Enter password again:
Enter permission (A)dmin, (O)perations, (M)onitor [A]?
Do you want to add Technical Support access? (Yes or [No]):

Enter password
Specifies the access password for the user. Limited to 80 alphanumeric characters and is case-sensitive.

Enter password again
Confirms the access password for the user.

Enter permission
Specifies the permission level for the user: A, O, or M (see Table 8).

v25-bis-address
Adds the local and remote numbers of the V.25bis end-points that communicate with the router. The network address-name can be anything, such as a description of the port. You can use any string of up to 23 printable ASCII characters. The network-dial-address is the telephone number of the local or destination port. For more information, see "Using the V.25bis Network Interface".
Note:You can use punctuation, such as parentheses and dashes, but the punctuation is not significant (the router uses only the numbers).
Example: add v25-bis-address
 remote-site baltimore 1-909-555-0983

Boot

Use the boot command to enter the Boot CONFIG command environment. For Boot CONFIG information, see "Using BOOT Config to Perform Change Management".

Syntax:

boot
 

Change

Use the change command to modify an interface in the configuration,change your own password, or change user information.

Syntax:

 change 
device . . .

password

ppp_user . . .

tunnel-profile

device device_type
With the change device command you can:

When the target slot is occupied:

  1. If you select the "swap" option, the source and target slots are swapped in all the interface records in which they appear.

  2. If you select the "replace" option is selected, the interface configuration for slot x will become the interface configuration for slot y. Interface records for slot y will be deleted.

When the target port is occupied:

  1. If you select the "swap" option, the source and target ports can be swapped in their respective interface records if their hardware types in these interface records are identical. For example, 1-port ISDN T1/J1.

  2. If you select the "replace" option, the interface configuration for slot x port u becomes the interface configuration for slot y port v. The interface record for slot y port v is deleted.
Note:An Ethernet or Token Ring adapter card requires two empty slots if it is installed in slot 3, 4, 7, or 8. Therefore a Token Ring or Ethernet adapter can be installed in slot 3 or 4 (or slot 7 or 8) only if both slots 3 and 4 (or 7 and 8) are unoccupied.

If you try to change the slot of a Token Ring or Ethernet adapter to slot 3 or 4 (or 7 or 8) when both 3 and 4 (or 7 and 8) are not unoccupied, the change is not accepted and a warning message is issued as shown in the example "Change slot 6 on interface 1 to unoccupied slot 8" on page ***.

Example - Change (replace) slot 1 on interface 1 to occupied slot 2:

Config>list dev
Ifc 0 CHARM ATM                       Slot: 2  Port: 1
Ifc 1 CHARM ATM                       Slot: 1  Port: 1
 
Config>change device
Which configured slot would you like to change? (1, 2) [2]? 1
Which slot would you like to change to? (1-2)  [1]? 2
 
Configuration for slot 2 already exists. You can:
a - abort this operation
r - replace configuration
    (Interface configuration for slot 1 will become interface
     configuration for slot 2.  Interface records for slot 2
     will be deleted!)
s - swap configuration (slot 1 will be swapped with slot 2.)
r
 
Moved slot 2 to slot 1 in 1 intf (port) record...
 
Config>list dev
Ifc 0 CHARM ATM                       Slot: 2  Port: 1

Example - Change slot 5 on interface 0 to unoccupied slot 7:

Config>list dev
Ifc 0 Token Ring                      Slot: 5  Port: 1
Ifc 1 Token Ring                      Slot: 6  Port: 1
Ifc 2 Token Ring                      Slot: 1  Port: 1
Ifc 3 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 0
Ifc 4 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 1
Ifc 5 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 2
Ifc 6 6 port V.35/V.36 PPP            Slot: 3  Port: 0
Ifc 7 6 port V.35/V.36 PPP            Slot: 3  Port: 5
Ifc 8 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 0
 
Config>change device
Which configured slot would you like to change? (1, 2, 3, 4, 5, 6)[1]? 5
Change all ports on slot # 5 (Yes or No)? [Yes]: y
Which slot would you like to change to? (1-8)  [1]? 7
 
Changed slot 5 to slot 7 in 1 intf (port) record...
 
Config>list dev
Ifc 0 Token Ring                      Slot: 7  Port: 1
Ifc 1 Token Ring                      Slot: 6  Port: 1
Ifc 2 Token Ring                      Slot: 1  Port: 1
Ifc 3 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 0
Ifc 4 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 1
Ifc 5 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 2
Ifc 6 6 port V.35/V.36 PPP            Slot: 3  Port: 0
Ifc 7 6 port V.35/V.36 PPP            Slot: 3  Port: 5
Ifc 8 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 0
 

Interface 0 is now changed to slot 7.

Example - Change slot 6 on interface 1 to unoccupied slot 8:

Config>change device
Which configured slot would you like to change? (1, 2, 3, 4, 6, 7)[1]? 6
Change all ports on slot # 6 (Yes or No)? [Yes]: y
Which slot would you like to change to? (1-8)  [1]? 8
 
Cannot add Token Ring to slot 8.
Slot 7 is occupied so Token Ring cannot be added in slot 8.
Note:See the note on 2 for requirements for changing slots 3, 4, 7, and 8 for Token Ring or Ethernet.

Example - Swap slot 6 on interface 1 to occupied slot 1:

Config>change device
Which configured slot would you like to change? (1, 2, 3, 4, 6, 7) [1] 6
Change all ports on slot # 6 (Yes or No)? [Yes]: y
Which slot would you like to change to? (1-8)  [1]? 1
 
Configuration for slot 1 already exists. You can:
a - abort this operation
r - replace configuration
    (Interface configuration for slot 6 will become interface
     configuration for slot 1.  Interface records for slot 1
     will be deleted!)
s - swap configuration (slot 1 will be swapped with slot 6.)
s
 
Swapped slot 6 with slot 1 in 1 port record...
 
Config>list dev
Ifc 0 Token Ring                      Slot: 7  Port: 1
Ifc 1 Token Ring                      Slot: 1  Port: 1
Ifc 2 Token Ring                      Slot: 6  Port: 1
Ifc 3 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 0
Ifc 4 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 1
Ifc 5 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 2
Ifc 6 6 port V.35/V.36 PPP            Slot: 3  Port: 0
Ifc 7 6 port V.35/V.36 PPP            Slot: 3  Port: 5
Ifc 8 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 0

The configurations for interface 2 and interface 1 are swapped.

Example - Slot 1 on interface 1 replaces slot 6, interface 1 is deleted:

Config>change device
Which configured slot would you like to change? (1, 2, 3, 4, 6, 7) [1] 6
Change all ports on slot # 6 (Yes or No)? [Yes]: y
Which slot would you like to change to? (1-8)  [1]? 1
 
Configuration for slot 1 already exists. You can:
a - abort this operation
r - replace configuration
    (Interface configuration for slot 6 will become interface
     configuration for slot 1.  Interface records for slot 1
     will be deleted!)
s - swap configuration (slot 1 will be swapped with slot 6.)
r
 
Moved slot 6 to slot 1 in 1 intf (port) record...
 
Config>list dev
Ifc 0 Token Ring                      Slot: 7  Port: 1
Ifc 1 Token Ring                      Slot: 1  Port: 1
Ifc 2 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 0
Ifc 3 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 1
Ifc 4 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 2
Ifc 5 6 port V.35/V.36 PPP            Slot: 3  Port: 0
Ifc 6 6 port V.35/V.36 PPP            Slot: 3  Port: 5
Ifc 7 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 0

The slot 6 record replaces the original slot 1 record and the other interfaces are renumbered.

Example - Change slot 2 to unoccupied slot 5:

Config>change device
Which configured slot would you like to change? (1, 2, 3, 4, 7) [1]? 2
Change all ports on slot # 2 (Yes or No)? [Yes]: y
Which slot would you like to change to? (1-8)  [1]? 5
 
Changed slot 2 to slot 5 in 3 intf (port) records...
 
Config>list dev
Ifc 0 Token Ring                      Slot: 7  Port: 1
Ifc 1 Token Ring                      Slot: 1  Port: 1
Ifc 2 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 0
Ifc 3 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 1
Ifc 4 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 2
Ifc 5 6 port V.35/V.36 PPP            Slot: 3  Port: 0
Ifc 6 6 port V.35/V.36 PPP            Slot: 3  Port: 5
Ifc 7 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 0

Interfaces 2, 3 and 4 that were previously configured in slot 2 are now configured in slot 5.

Example - Change port 1 slot 5 to port 0 in unoccupied slot 2:

Config>change device
Which configured slot would you like to change? (1, 3, 4, 5, 7)  [1]? 5
Change all ports on slot # 5 (Yes or No)? [Yes]: n
Which port would you like to change in slot 5? (0, 1, 2) [0]? 1
Which slot would you like to change to? (1-8)  [1]? 2
Which port would you like port 1 in slot 5 to move to in slot2?#(0-7)[0]? 0
 
Changed slot 5 port 1 to slot 2 port 0...
 
Config>list dev
Ifc 0 Token Ring                      Slot: 7  Port: 1
Ifc 1 Token Ring                      Slot: 1  Port: 1
Ifc 2 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 0
Ifc 3 8 port EIA-232E/V.24 PPP        Slot: 2  Port: 0
Ifc 4 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 2
Ifc 5 6 port V.35/V.36 PPP            Slot: 3  Port: 0
Ifc 6 6 port V.35/V.36 PPP            Slot: 3  Port: 5
Ifc 7 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 0

Interface 3, which was at slot 5 - port 1, is changed to slot 2 port 0.

Example - Change port 0 slot 2 to port 5 in slot 3 (different hardware types):

Config>change device
Which configured slot would you like to change? (1, 2, 3, 4, 5, 7) [1]? 2
Change all ports on slot # 2 (Yes or No)? [Yes]: n
Which port would you like to change in slot 2? (0) [0]? 0
Which slot would you like to change to? (1-8)  [1]? 3
Which port would you like port 0 in slot 2 to move to in slot 3? #(0-7) [0] 5
 
Aborting - source and target slots of different type.

Example - Change port 0 slot 2 to port 5 in slot 4 (same hardware types):

Config>change device
Which configured slot would you like to change? (1, 2, 3, 4, 5, 7) [1]? 2
Change all ports on slot # 2 (Yes or No)? [Yes]: n
Which port would you like to change in slot 2? (0) [0]? 0
Which slot would you like to change to? (1-8)  [1]? 4
Which port would you like port 0 in slot 2 to move to in slot 4? #(0-7)[0] 5
 
Changed slot 2 port 0 to slot 4 port 5...
 
Config>list dev
Ifc 0 Token Ring                      Slot: 7  Port: 1
Ifc 1 Token Ring                      Slot: 1  Port: 1
Ifc 2 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 0
Ifc 3 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 5
Ifc 4 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 2
Ifc 5 6 port V.35/V.36 PPP            Slot: 3  Port: 0
Ifc 6 6 port V.35/V.36 PPP            Slot: 3  Port: 5
Ifc 7 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 0

Interface 3 which was at port 0, slot 2 is changed to port 5, slot 4.

Example - Change port 5 slot 4 to port 1 in slot 4 (same slots):

Config>change device
Which configured slot would you like to change? (1, 3, 4, 5, 7) [1]? 4
Change all ports on slot # 4 (Yes or No)? [Yes]: n
Which port would you like to change in slot 4? (0, 5) [0]? 5
Which slot would you like to change to? (1-8)  [1]? 4
Which port would you like port 5 in slot 4 to move to in slot 4? #(0-7) [0] 1
 
Changed slot 4 port 5 to slot 4 port 1...
 
Config>list dev
Ifc 0 Token Ring                      Slot: 7  Port: 1
Ifc 1 Token Ring                      Slot: 1  Port: 1
Ifc 2 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 0
Ifc 3 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 1
Ifc 4 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 2
Ifc 5 6 port V.35/V.36 PPP            Slot: 3  Port: 0
Ifc 6 6 port V.35/V.36 PPP            Slot: 3  Port: 5
Ifc 7 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 0

Interface 3 is now at port 1, slot 4.

Example - Change (swap) port 1 slot 4 to occupied port 0 in slot 5:

Config>change device
Which configured slot would you like to change? (1, 3, 4, 5, 7) [1]? 4
Change all ports on slot # 4 (Yes or No)? [Yes]: n
Which port would you like to change in slot 4? (0, 1) [0]? 1
Which slot would you like to change to? (1-8)  [1]? 5
Which port would you like port 1 in slot 4 to move to in slot 5? #(0-7) [0] 0
 
Configuration for slot 5 (port 0) already exists. You can:
a - abort this operation
r - replace configuration
    (Interface record for slot 4 port 1 will become interface
     configuration for slot 5 port 0.  The interface record for
     slot 5 port 0 will be deleted!)
s - swap configuration (slot 5 port 0 will be swapped with slot 4
    port 1.)
s
 
Swapped slot 4 port 1 with slot 5 port 0...
 
Config>list dev
Ifc 0 Token Ring                      Slot: 7  Port: 1
Ifc 1 Token Ring                      Slot: 1  Port: 1
Ifc 2 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 1
Ifc 3 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 0
Ifc 4 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 2
Ifc 5 6 port V.35/V.36 PPP            Slot: 3  Port: 0
Ifc 6 6 port V.35/V.36 PPP            Slot: 3  Port: 5
Ifc 7 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 0

Interface 2 and interface 3 have swapped their port and slot configurations.

Example - Change (replace) port 1 slot 4 to occupied port 0 in slot 5:

Config>change device
Which configured slot would you like to change? (1, 3, 4, 5, 7) [1]? 4
Change all ports on slot # 4 (Yes or No)? [Yes]: n
Which port would you like to change in slot 4? (0, 1) [0]? 1
Which slot would you like to change to? (1-8)  [1]? 5
Which port would you like port 1 in slot 4 to move to in slot 5? #(0-7) [0] 0
 
Configuration for slot 5 (port 0) already exists. You can:
a - abort this operation
r - replace configuration
    (Interface configuration for slot 4 port 1 will become interface
    configuration for slot 5 port 0.  The interface record for
    slot 5 port 0 will be deleted!)
s - swap configuration (slot 5 port 0 will be swapped with slot 4
    port 1.)
r
 
Moved slot 4 port 1 to slot 5 port 0...
 
Config>list dev
Ifc 0 Token Ring                      Slot: 7  Port: 1
Ifc 1 Token Ring                      Slot: 1  Port: 1
Ifc 2 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 0
Ifc 3 8 port EIA-232E/V.24 PPP        Slot: 5  Port: 2
Ifc 4 6 port V.35/V.36 PPP            Slot: 3  Port: 0
Ifc 5 6 port V.35/V.36 PPP            Slot: 3  Port: 5
Ifc 6 8 port EIA-232E/V.24 PPP        Slot: 4  Port: 0
 

Interface 2 is configured to slot 5 - port 0. The original interface 3 is deleted and the other interfaces are renumbered.

password
Modifies the password of the user who is now logged in.
Note:To change a user password, you must have administrative permission.

Example:

change password
Enter current password:
Enter new password:
Enter new password again:

Enter current password
Specifies your current password.

Enter new password
Specifies your new password.

Enter new password again
Specifies your new password again for confirmation. If your confirmation does not match the previous new password, the old password remains in effect.

ppp_user
Changes the information for a specific PPP user.

Syntax:

change ppp_user
encryption-key

parameters

password

encryption-key
Changes the encryption key for a PPP user. The following example shows the dialog for changing an encryption key.

Example - Change Encryption key:

Config>change ppp_user encryption-key
Enter user name:  []? leslie
Enable encryption for this user/port (y/n) [No]:y
Encryption key should be 16 characters long.
Encryption Key (16 characters ) in Hex(0-9, a-f, A-F):
Encryption Key again (16 characters) in Hex(0-9, a-f, A-F):
User 'leslie' has been updated
Config>

parameters
Changes all of the ppp-user options for a user. This parameter works similar to the add ppp_user except that the values shown within the [ ] are the current values and the change command does not verify the changes or list them back to you when you are done. See "Add" for details about the add ppp_user command.

password
Changes the password for the PPP user.

Example - Change password:

Config>change ppp_user password
Enter user name:  []? sam
Password:
Enter password again:
User 'sam' has been updated
Config>

user
Modifies the user information that was previously configured with the add user command.
Note:To change a user, you must have administrative permission.

Example:

change user
User name: []
Change password? (Yes or No)
Change permission? (Yes or [No])

tunnel-profile
Changes the configuration for a tunnel peer.
Config>change tunnel-profile
Enter name:  []? lac.org
Enter hostname to use when connecting to this peer: [lns.org]?
set shared secret? (Yes, No): [No]
Tunnel-Server endpoint address: [11.0.0.1]? 11.0.0.2
 
profile 'lac.org' has been updated
Config>

Clear

Use the clear command to delete the device's configuration information from nonvolatile configuration memory.

Attention:  Use this command only after calling your service representative.

Syntax:

clear
all

ap2 (AppleTalk 2)

arp (ARP)

asrt (Adaptive Source Route Protocol)

appn (Advanced Peer-to-Peer Networking)

atm (Asynchronous Transfer Mode)

auth (Authentication)

bgp (Border Gateway Protocol)

boot

brs (Bandwidth Reservation)

callback

cmprs (Data Compression)

dls (Data Link Switching)

device

dialer-circuit

dn (DECnet)

els (Event Logging System Information)

fr (Frame Relay)

gsmp (OSI)

hdlc

hod (Host On-Demand Client Cache) *

hostname

ip (IP)

ip-security

ipv6

ipx (Novell IPX)

isdn

l2tp

lnm

mcf

named-profiles

nat

ndp6

ndr

osi (OSI)

ospf (OSPF routing protocol)

ppp (Point-to-Point)

prompt

rip6

rsvp

sdlc

snmp

srly (SDLC Relay)

tcp/ip-host

time (Time of day information)

tsf (Thin Server)

user

v25bis

vines (Banyan VINES)

webc (Web Server Cache) *

wrs (WAN Restoral feature)

x25

xtp
*Note:HOD and WEBC do not coexist in the same software image.

To clear a process from nonvolatile configuration memory, enter the clear command and the process name. To clear all information from configuration memory, except for device information, use the clear all command. To clear all information, including the device information, use the clear all command and then the clear device command.

The clear user command clears all user information except the device console login information. This is left as enabled (if it was configured as enabled) even though the default value is "disabled".

Notes:

  1. To clear user information, you must have administrative permission.

  2. There may be other items in the list, depending upon what is included in the software load.

Example: clear els

You are about to clear all Event Logging configuration information
Are you sure you want to do this (Yes or No):
Note:The previous message appears for any parameter configuration you are clearing.

Delete

Use the delete command to remove an interface or range of interfaces from the list of devices stored in the configuration, or to remove a user. To use the delete command, you must have administrative permission.

Syntax:

delete
coprocessor . . .

interface . . .

dump-files

isdn-address

ppp_user . . .

tunnel

user . . .

v25-bis-address

interface [intfc# or intfc#range]
To delete an interface, enter the interface or network number as part of the command. (Only devices that were added with the add device command can be deleted.) To obtain the interface number that the device assigns, use the list device command.

The delete interface command deletes the device configuration and any protocol information for that interface. However, the device will continue to run the previous configuration until it is reloaded.

If deleting a base ISDN interface or a base ATM interface, all virtual interfaces running on that base net will also be deleted. So, any dial circuits configured on a base ISDN interface will be removed when the ISDN interface is deleted. Also, when deleting an ATM base net, all LAN Emulation Clients running on the base ATM interface will be deleted.

To delete a range of interfaces, specify the first and last interface in the range separated by a hyphen, as shown in the following example:

delete interface 13-21

You can also enter an interface number or range of interface numbers, when prompted.

interface [intfc# or intfc#range]
To delete an interface, enter the interface or network number as part of the command. (Only devices that were added with the add device command can be deleted.) To obtain the interface number that the device assigns, use the list device command.

The delete interface command deletes the device configuration and any protocol information for that interface. However, the device will continue to run the previous configuration until it is reloaded.

If deleting a base ISDN interface or a base ATM interface, all virtual interfaces running on that base net will also be deleted. So, any dial circuits configured on a base ISDN interface will be removed when the ISDN interface is deleted. Also, when deleting an ATM base net, all LAN Emulation Clients running on the base ATM interface will be deleted.

To delete a range of interfaces, specify the first and last interface in the range separated by a hyphen, as shown in the following example:

delete interface 13-21

You can also enter an interface number or range of interface numbers, when prompted.

isdn-address address-name
Removes a previously added ISDN address.
Note:If the address-name contains spaces (for example, remote site XYZ), you cannot enter the command on one line. Type delete isdn-address and press Return. Then enter the name when prompted.

ppp_user user_name
Deletes a user from the PPP user data base.

tunnel-profile
Deletes a tunnel from the tunnel profile database.

user user_name
Removes user access to the device for the specified user.

v25-bis-address address-name
Removes a previously added V25bis address.
Note:If the address-name contains spaces (for example, remote site Baltimore), you cannot enter the command on one line. Type delete v25-bis-address and press Return. Then enter the name when prompted.

Disable

Use the disable command to disable command completion, login from a remote console, disables modem use

Syntax:

disable
command-completion

console-login

dump-memory . . .

interface . . .

reboot-system . . .

command-completion

Use the disable command-completion command to disable the automatic command completion function. See "Command Completion" for a discussion of the automatic command completion function.
Note:Command completion defaults to disabled for existing configurations and defaults to enabled for new configurations. If you are using an existing configuration and want to use command completion, you need to use the enable command-completion command to enable this function.

console-login
Disables the user from being prompted for a user ID and password on the physical console. The default is disabled.

interface interface#
Causes the specified interface to be disabled after issuing the reload command. The default is enabled.

dump-memory
Disables the dumping of system memory to the installed hard disk when a serious error occurs.

reboot-system
Disables the rebooting of the system when a serious error occurs. This may be desirable if the network service personnel wish to troubleshoot the error on-line. System rebooting cannot be disabled unless memory dumping is also disabled. If you attempt to disable system rebooting while memory dumping is enabled, system rebooting is aborted and the following message is displayed:
  System reboot not disabled:  memory dumping must be disabled first

Enable

Use the enable command to enable command completion, login from a remote console, disables modem use

Syntax:

 enable 
command-completion

console-login

dump-memory . . .

interface . . .

reboot-system . . .

command-completion

Use the enable command-completion command to enable the automatic command completion function, which assists with the command syntax. See "Command Completion" for a discussion of the automatic command completion function.

console-login
Enables the user to be prompted for a user ID and password on the physical console. This is useful for security situations. If you do not configure any administrative users and you enable this feature, the following message appears:
Warning: Console login is disabled until an
administrative user is added.
Attention:Before enabling console login, save the configuration with console login disabled. If login authentication is set to a remote server using Radius or Tacacs+ and the device is unable to reach the authentication server, then access to the device is denied. By disabling the console login, a lock-out situation is prevented.

dump-memory
Enables the dumping of system memory to the installed hard disk if a serious error occurs. This may be desirable so that the state of the unit at the time of the error can be preserved for troubleshooting later. The dump memory function cannot be enabled unless system rebooting is enabled. If you attempt to enable the dump memory function while system rebooting is disabled, the dump memory function is not enabled and the following message is displayed:
System memory dump function not enabled:  rebooting must be enabled first

If you configured system dumping to save the first 3 dump files and 3 dump files already exist on the hard drive, the system displays the following message when you enable dump memory:

*** System dump cannot be enabled until the    *** 
*** existing dump files are deleted.           *** 

See the set dump enable-mode and set dump save-mode commands.

Example:

Config> enable dump 
 
Current System Dump Status: 
   System dump is currently disabled. 
   Number of existing dump files:  0 
 
Enable system memory dumping? [No]: Yes 
 
Current System Dump Status: 
   System dump is currently enabled. 
   Number of existing dump files:  0
Note:If you enter this command and a hard drive is not available, you will receive a message indicating that the drive is unavailable.

interface interface#
Causes the interface to be enabled after issuing the reload command.

modem-control [carrier-wait or ring-wait] [service1 or service2]
Sets up the device for login on the physical console, if the physical console is connected to the device through a modem. Before using this command, be sure to:

Set your modem for auto-answer.

Verify that the console baud rate is equal to the modem baud rate.

Verify that the cable connecting the modem to the device is configured correctly.

Turn echo off by using the ATE0 command.

Run in quiet mode by using the ATQ1 command.

Verify that any necessary jumpers are set. Refer to your device's User's Guide more information. The device automatically hangs up the modem when you log out. Also, if your modem becomes disconnected from the device while you are using it, the device logs you out.

Specify the service port for both the enable modem-control carrier-wait and the enable modem-control ring-wait commands. For devices with two service ports, also specify to which service port you connected the modem, either service1 or service2. To enable both service ports, enable them separately.
Note:No console connection can be made with the device after enabling modem control unless you clear all configuration and restart the device.

You can tell the device to wait for the carrier-detect signal from the modem before sending Request to Send. This is the standard method of modem control.

You can tell the device to wait for the ring-indication signal before raising Request to Send or Data Terminal Ready. This is provided for countries requiring an earlier handshake.

Example:

Config> enable modem-control carrier-wait service1

reboot-system
Enables the rebooting of the system when a serious error occurs.

Event

Use the event command to enter the Event Logging System (ELS) environment so that you can define the messages that will appear on the console. Refer to "Using the Event Logging System (ELS)" for information about ELS.

Syntax:

event
 

Feature

Use the feature command to access configuration commands for specific device features outside of the protocol and network interface configuration processes.

Syntax:

feature
[feature# or feature-short-name]

All 2216 features have commands that are executed by:

The procedure for accessing these processes is the same for all features. The following information describes the procedure.

Enter a question mark after the feature command to obtain a listing of the features available for your software release.

To access a feature's configuration prompt, enter the feature command followed by the feature number or short name. Table 9 lists available feature numbers and names.

Table 9. IBM 2216 Feature Numbers and Names

Feature
Number



Feature
Short Name



Accesses the following
feature configuration process


0 WRS WAN Restoral/Reroute
1 BRS Bandwidth Reservation
2 MCF MAC Filtering
4 VCRM Virtual Circuit and Resource Management
7 ES Encoding Subsystem
8 NDR Network Dispatcher
9 DIALs Dial-In-Access to LANs
10 AUTH Authentication
11 IPSec IP Security feature user configuration
12 LAYER Layer 2 Tunneling Protocol, Layer 2 Filtering, Point-to-Point Tunneling Protocol
13 NAT Network Address Translator user configuration
14 TSF Thin Server Function
15 WEBC Web Server Cache1
15 HOD Host on Demand Client Cache1
16 DHCP DHCP Services
20 POLICY Policy feature
21 DS Differentiated services
1HOD and WEBC do not coexist in the same software image; that is why they have the same feature number.

Once you access the configuration prompt for a feature, you can begin entering specific configuration commands for the feature. To return to the CONFIG prompt, enter the exit command at the feature's configuration prompt.

List

Use the list command to display configuration information for all network interfaces, or configuration information for the device.

Syntax:

list
configuration

devices

named-profile

isdn-address

patches . . .

ppp_users . . .

tunnel-profile

users . . .

v25-bis-address

vpd

configuration
Displays configuration information about the device.

Example: list configuration

 
Hostname: [none]
Maximum packet size: [autoconfigured]
Maximum number of global buffers: [autoconfigured]
Number of spare interfaces: 0
Console inactivity timer (minutes): 0
Physical console login: disabled
System rebooting on error: disabled
System memory dumping: disabled
Contact person for this node: [none]
Location of this node: [none]
 
Configurable Protocols:
Num Name  Protocol
0   IP    DOD-IP
3   ARP   Address Resolution
4   DN    DNA Phase IV
6   VIN   Banyan Vines
7   IPX   NetWare IPX
8   OSI   ISO CLNP/ESIS/ISIS
9   DVM   Distance Vector Multicast Routing Protocol
10  BGP   Border Gateway Protocol
11  SNMP  Simple Network Management Protocol
12  OSPF  Open SPF-Based Routing Protocol
20  SDLC  SDLC/HDLC-Relay
22  AP2   AppleTalk Phase 2
23  ASRT  Adaptive Source Routing Transparent Enhanced Bridge
24  HST   TCP/IP Host Services
25  LNM   LAN Network Manager
26  DLS   Data Link Switching
27  XTP   X.25 Transport Protocol
28  APPN  Advanced Peer-to-Peer Networking [HPR]
29  NHRP  Next Hop Routing Protocol
30  APPN  Advanced Peer-to-Peer Networking [ISR]
 
Configurable Features:
Num Name  Feature
0   WRS   WAN Restoral
1   BRS   Bandwidth Reservation
2   MCF   MAC Filtering
6   QOS   Quality of Service
7   CMPRS Data Compression Subsystem
8   NDR   Network Dispatching Router
10  AUTH  Authentication
14  TSF   Thin Server Function
 
26176 bytes of configuration memory free

devices [device or devicerange]
Displays the relationship between an interface number and the hardware interface. You can also use this command to check that a device was added correctly issuing the add command.

You can also specify a range of devices to list as shown in the following example:

list dev 2-5
Ifc 2 Token Ring                      Slot: 2  Port: 1
Ifc 3 Token Ring                      Slot: 2  Port: 2
Ifc 4 Ethernet                        Slot: 4  Port: 1
Ifc 5 Ethernet                        Slot: 4  Port: 2
Note:If you do not specify an interface number or a range of interfaces, all interfaces are displayed.

Example: list devices

Ifc 0 Token Ring                      Slot: 1  Port: 1
Ifc 1 Token Ring                      Slot: 1  Port: 2
Ifc 2 Token Ring                      Slot: 2  Port: 1
Ifc 3 Token Ring                      Slot: 2  Port: 2
Ifc 4 Ethernet                        Slot: 4  Port: 1
Ifc 5 Ethernet                        Slot: 4  Port: 2
Ifc 6 Ethernet                        Slot: 5  Port: 1
Ifc 7 Ethernet                        Slot: 5  Port: 2
Ifc 8 Ethernet                        Slot: 6  Port: 1
Ifc 9 Ethernet                        Slot: 6  Port: 2
Ifc 10 V.35/V.36 Frame Relay          Slot: 8  Port: 0
Ifc 11 V.35/V.36 X.25                 Slot: 8  Port: 1
Ifc 12 V.35/V.36 PPP                  Slot: 8  Port: 2
Ifc 13 V.35/V.36 PPP                  Slot: 8  Port: 3
Ifc 14 V.35/V.36 PPP                  Slot: 8  Port: 4
Ifc 15 V.35/V.36 PPP                  Slot: 8  Port: 5
Note:The number of receive buffers noted are exceptions from the receive buffer defaults. The set receive buffers command is discussed under "Set".

isdn-address
Displays the current ISDN address configurations.
Example: list isdn-address
Address assigned name     Network Address     Network Subdial Address
---------------------     ---------------     -----------------------
remote site XYZ            1 2345 67           98765
 

patches
Displays the values of patch variables that have been entered using the patch command.

Example:

list patches
Patched variable             Value
 
ping-size                    60
ping-ttl                     59
ethernet-security            3
 

ppp_users
Lists specific PPP user profile parameters.

Example: List of PPP users when DIALs is not in the software load

Config> list ppp_users
List (Name, Verb, User, Addr, Encr):
 
       PPP User Name: joe
     User IP Address: Interface Default
          Encryption: Not Enabled

Example: List of PPP users when DIALs is in the software load

Config> list ppp_users
List (Name, Verb, User, Addr, Call, Time, Dial, Encr):
 
       PPP User Name: joe
     User IP Address: Interface Default
      Net-Route Mask: 255.255.255.255
            Hostname: <undefined>
       Time-Allotted: Box Default
      Call-Back Type: Not Enabled
            Dial-Out: Not Enabled
          Encryption: Not Enabled

When you enter list ppp_users, the software will prompt you to enter one of the following:

Name
List all of the names in the database.

Verb
List verbose information about each user. List all information pertaining to each user profile.

User
List verbose information about a single user.

Addr (address)
List IP address information for each user, including IP Address, net mask and hostname.

Call (callback)
List callback information for each user, including the type of callback and number.

Time
List time allowed configured for each user.

Encr (encryption)
List whether encryption is enabled for each user.

tunnel-profile
Displays the tunnel-profile parameters.

Example:

Config>list tunnel-profile
 
Endpoint	Tunnel name	Hostname                        
11.0.0.192	lac		lns
 
1 TUNNEL record displayed.
 
Config>                                                             

Tunnel Name
Specifies the configured name for the peer.

Server Endpoint
The IP address of the peer.

Type
Specifies the type of peer connection.

Medium
Specifies the protocol that the tunnel is using.

Local Host Name
Specifies the name configured for use when connecting to the peer.

users
Displays the users configured to access the system.

Example:

list users
USER           PERMISSION
joe            operations
mary           administrative
peter          monitor

v25-bis-address
Displays the current V25bis address configurations. The V25bis address configuration consists of the network address and network address name for a local port (serial line interface) or destination port. The network address is the telephone number of the local or destination port. The network address name can be anything, such as the description of the port. See "Using the V.25bis Network Interface" for more information.
Example:
list v25-bis-address
Address assigned name             Network Address
---------------------             ---------------
v25-1                             8982800
v25-2                             8980001
delaware                          1-666-555-4444

vpd
Displays the hardware and software vital product data.

Load

Use the load command to list packages in the software load that are available but not configured, or packages that are configured in the software load. The load command is also used to add or delete a software package.

Syntax:

load
add package packagename

delete package packagename

list . . .

The software is divided into multiple load modules. These load modules are grouped into software packages. Some of these software packages are optional because, although they are shipped with the product, they are not automatically loaded.

Software packages containing encryption are available from the 2216 Web server accessible using the Internet.

To load and run optional software packages:

  1. Add the package using the load add command.

  2. Reboot. This action loads the optional software into the device's memory.

  3. Configure the optional software.

  4. Save the configuration.

  5. Reboot the device. This action enables the software with the new configuration.

add package packagename
Adds a software package to the software. The packagename is the name of the package of load modules you want to include in the software.

Example: load add package appn

delete package packagename
Removes a software package from the software. The packagename is the name of the package of load modules you want to remove from the software.

Example: load delete package appn

list
Lists either the packages in the software load that are available but not configured, or the packages that are configured in the software load. You can specify one of the following:

available
Lists the software packages in the current software load that are not configured.

configured
Lists the software packages in the current software load that are configured.

Network

Use the network command to enter the network interface configuration environment for supported networks. Enter the interface or network number as part of the command. (To obtain the interface number, use the CONFIG list device command.) The appropriate configuration prompt (for example, TKR Config>) will be displayed. See the network interface configuration chapters in this book for complete information on configuring your types of network interfaces.

Syntax:

network
interface#

Notes:

  1. If you change a user-configurable parameter, you may use the GWCON reset interface command, or you may reload the device for the change to take effect. To do so, enter the reload command at the OPCON prompt (*).

  2. Not all network interfaces are user-configurable. For interfaces that you cannot configure, you receive the message: That network is not configurable.

Patch

Use the patch command for modifying the device's global configuration. Patch variables are recorded in nonvolatile configuration memory and take effect immediately; you do not have to wait for the next restart of the device. This command should be used only for handling uncommon configurations. Anything that you commonly configure should still be handled by using the specific configuration commands. The following is a list of the current patch variables documented and supported for this release.

Syntax:

patch
bgp-subnets

dls-ignore-lfs

ethernet-security

filter-nr

ip-default-ttl

ip-mtu

lnm-link-via-tbport

more-lines

mosheap-lowmark

ospf-import-rate

ping-size

ping-ttl

ppp-echo

relax-jate

rip-static-suppress

tftp-max-rxto-time

tftp-min-rexmtime

bgp-subnets new value
If you want the BGP speaker to advertise subnet routes to its neighbors, set new value to 1. The default is 0.

dls-ignore-lfs new value
When set to 1, DLSw ignores the "largest frame" size bits in source-routed frames when setting up a circuit. This avoids circuit setup problems with some older LAN products that do not set these bits correctly. The default is 0.

ethernet-security new value
When set to a non-zero value, zeros the padding that is applied to Ethernet packets whose data portion is less than the physical minimum of 60 bytes. This may be required for security reasons. Default: 0.

filter-nr
Allows the NetBIOS "Name Recognized" to be filtered along with the current list of NetBIOS frames filtered by bridge code. NetBIOS Name filters will pass all NetBIOS packets that are not one of the following types: ADD_GROUP_NAME_QUERY, ADD_NAME_QUERY, DATAGRAM, NAME_QUERY. This parameter adds NAME_RECOGNIZED to the list of types.

ip-default-ttl #_of_packets
The TTL used in packets that are originated by the device. The default is 64.
Note:It is preferable to set this parameter with the set ttl IP configuration command. (See the "Set" section of the "Using and Configuring IP" chapter of Protocol Configuration and Monitoring Reference Volume 1 .) This patch variable remains for compatibility with configurations from older releases.

ip-mtu bytes
This parameter limits the IP MTU size to the specified value. When this parameter is set, the IP MTU size on a given network interface is set to the lesser of the ip-mtu value and the largest value that network interface's configured frame size can accommodate.

lnm-link-via-tbport new value
Allows LNM to link to a token-ring over an Ethernet transparent bridge (TB) port.

When set to 1, the LNM link is allowed.

When set to 0, the default, the LNM link is not allowed.

more-lines #_of_lines
The number of lines to display on the console when listing long output.

mosheap-lowmark new value
This parameter specifies the percentage of free MOS heap memory, at which the device notifies the operator that an out-of-memory error is imminent. This notification allows the operator to take action to free up MOS heap memory before the device receives an error and stops.

When the operator receives notification, the operator can reconfigure the device and then reboot, minimizing the outage to the network. Specifying 0 for this parameter suppresses this warning.

Valid Values: 0 to 100

Default Value: 10

ospf-import-rate rate
Number of routes imported per second.

ping-size bytes
The size of the data portion (that is, excluding IP and ICMP headers) of the ICMP PING packet that is sent via the IP>ping command. Default: 56 bytes. (The size of the PING data can also be entered as a parameter of the ping command as described in the "Ping" section of the "Monitoring IP" chapter of Protocol Configuration and Monitoring Reference Volume 1 .)

ping-ttl seconds
The TTL (time-to-live) sent in PINGs by the IP>ping command. Default: 64. (The TTL can also be entered as a parameter of the ping command as described in the "Ping" section of the "Monitoring IP" chapter of Protocol Configuration and Monitoring Reference Volume 1.

ppp-echo new value
When set to 1, the device will not send PPP Echo Requests on any PPP interface. PPP Echo Requests are sent to remote devices as part of PPP maintenance to ensure the remote device is operational. Consider enabling this variable when running PPP on a slow line and using that line to transmit large data packets such that the PPP maintenance packets are not exchanged often enough to keep the PPP interface up.

relax-jate
Relaxes JATE ISDN restriction.

rip-static-suppress new value
When set to a non-zero value, static routes will not be advertised by RIP over a given interface unless the IP config> enable send static command is given for the interface. This changes the semantics of the enable send static command. When rip-static-suppress is equal to 0 (the default), the list of the routes advertised via RIP is the union of those specified by the interface's RIP flags.

tftp-max-rxto-time

tftp-max-rxto-time allows you to specify the maximum time to wait for a response from the partner before failing the transfer. Default value: 5 minutes

The units for this patch variable are seconds.

tftp-min-rexmtime

tftp-min-rexmtime allows you to specify the smallest interval of time to wait for a response from the partner before retransmitting the last packet sent. Default value: 1

The units for this patch variable are seconds.

Note:You must specify the complete name of the patch variable that you want to change. You cannot use an abbreviated syntax for the patch name.

Performance

Use the performance command at the Config> prompt to enter the configuration environment for performance. See "Configuring and Monitoring Performance" for more information.

performance

Protocol

Use the protocol command at the Config> prompt to enter the configuration environment for the protocol software installed in the device.

Syntax:

protocol
[prot# or prot_name]

The protocol command followed by the desired protocol number or short name lets you enter a protocol's command environment. After you enter this command, the prompt of the specified protocol appears. From the prompt, you can enter commands specific to that protocol. To return to Config>, enter the exit command.

Notes:

  1. To see the names and numbers of the protocols in your software load, at the Config> prompt, enter list configuration.

  2. When you change a user-configurable parameter, you may be able to use the protocol's GWCON reset command, or you may have to restart the device for the change to take effect. To do so, enter the reload command at the OPCON prompt (*).

    The changes you make through CONFIG are kept in a configuration database in nonvolatile memory and are recalled when you restart the device.

Qconfig

Use the qconfig command to initiate Quick Config. Quick Config allows you to configure parameters for bridging and routing protocols without entering separate configuration environments.

Syntax:

qconfig
 
Note:For complete information on using the Quick Config software provided with your device, see Appendix A, Quick Configuration Reference.

Set

Use the set command to configure various system-wide parameters.

Syntax:

set
contact-person . . .

data-link . . .

down-notify . . .

dump enable-mode

dump save-mode

global-buffers

hostname

inactivity-timer

input-low-water

location . . .

logging level

packet-size

prompt

receive-buffers

spare-interfaces

contact-person sysContact
Sets the name or identification of the contact person for this managed SNMP node. There is a limit of 80 characters for the sysContact name length.

This variable is for information purposes only and has no effect on device operation. It is useful for SNMP management identification of the system.

data-link type interface#
Select the data link type for a serial interface or a dial circuit interface. The type can be one of:

Notes:

  1. PPP, SDLC, and Frame Relay are the only data-links supported on dial circuit interfaces. X.25 is supported on ISDN BRI D-channel only.

  2. All data-link types can be used on the 8-port EIA 232E adapter, 6-port V.35/V.36 adapter, and the 8-port X.21 adapter except for V.25bis which can only be used with the EIA 232E adapter.

Interface# is the number of the interface you are configuring.

down-notify interface# # of seconds
Allows the user to specify the number of seconds before declaring an interface as being down. The normal maintenance packet interval is 3 seconds, and it takes four maintenance failures to declare the interface as down.

The set down-notify command is used primarily when tunneling LLC traffic over an IP network using OSPF. If an interface goes down, OSPF cannot detect it fast enough because of the length of time that it takes for an interface to be declared down. Therefore, LLC sessions would begin to timeout. You can set the down-notify timer to a lower value, allowing OSPF to sense that an interface is down quicker. This enables an alternate route to be chosen more quickly, which will prevent the LLC sessions from timing out.
Note:If the set down-notify command is executed on one end of a serial link, the same command must be performed at the other end of the link or the link may not come up and stay up.

Interface#
The number of the interface you are configuring.

# of seconds
The down notification time value that specifies the maximum time that will elapse before a down interface is marked as such. Large values will cause the device to ignore transient connection problems, and smaller values will cause the device to react more quickly. The range of values is 1 to 300 seconds and the default is 0, which sets the 3-second period. Setting the down notification time to 0 will restore the default time for that interface.

The list devices command will show the down notification time setting for any interface that has the default value overridden.

dump enable-mode
Specifies whether dumping is enabled following the next system dump. If you configure the save mode (see the set dump save-mode command) to save the first three dumps and the system has already created the third dump file, dumping is disabled regardless of your specification. At the time the system creates the third dump file, you will receive the following message:
Active Dump Detected. 
Dump Compression in Progress, please be patient ... 
  
*** System dumping is being DISABLED because dumping is *** 
*** configured to save the 3 initial dumps, but 3       *** 
*** dump files already exist.                           ***

Example:

Config> set dump enable-mode 
 
Current System Dump Settings: 
   Disable System Dump following the next system dump. 
   Save the last 3 (most recent) dump files. 
 
Do you want to change system dump enable-mode to 
re-enable System Dump following the next system dump ? (Yes, No): [No] Yes 
 
Current System Dump Settings: 
   Re-enable System Dump following the next system dump. 
   Save the last 3 (most recent) dump files. 
 
Current System Dump Status: 
   System dump is currently enabled. 
   Number of existing dump files:  2

Default value: disable
Note:Dumping is enabled with the enable dump-memory command.

dump save-mode
Specifies whether to save the first three (initial) system dump files or the last three (most recent). See the dump enable-mode for a consideration for using recent mode as opposed to initial mode.

Example:

Config> set dump save-mode 
 
Current System Dump Settings: 
   Re-enable System Dump following the next system dump. 
   Save the last 3 (most recent) dump files. 
 
Do you want to change system dump save-mode to 
save the first (initial) dump files ? (Yes, No): [No] Yes 
 
Current System Dump Settings: 
   Re-enable System Dump following the next system dump. 
   Save the first 3 (initial) dump files, then disable system dump. 
 
Current System Dump Status: 
   System dump is currently enabled. 
   Number of existing dump files:  2

Default value: recent

global-buffers max#
Sets the maximum number of global packet buffers, which are the packet buffers used for locally originated packets. The default is to autoconfigure for the maximum number of buffers (up to 10000). To restore the default, set the value to 0. To display the setting for global-buffers, use the list configuration command.

hostname name
Adds or changes the device name. The device name is for identification only; it does not affect any device addresses. The name must be less than 78 characters and is case sensitive.

inactivity-timer #_of_min
Changes the setting of the Inactivity Timer. The Inactivity Timer logs out a user if the remote or physical console is inactive for the period of time specified in this command. This command affects only consoles that require login. The default setting of 0 turns the inactivity timer off, indicating that no logoff is performed, no matter how long a console remains inactive.

input-low-water interface# low_ #_of_receive_buffers
Allows you to configure an interface's low threshold for receive buffers. When the current number of receive buffers for an interface is less than the interface's low threshold, the packet is eligible for flow control (dropping) if the packet is queued on an output queue that has reached its high threshold (fair) value. See the description of the GWCON queue command for more details on flow control.

Lowering the low threshold value will make it less likely that packets from this interface will be dropped when sent on congested networks. However, lowering the value may negatively affect performance if underruns occur because the receive buffer queue is empty. Raising the value has the opposite effect. To determine if underruns are occurring, use the GWCON interface command and specify the interface number. To determine if packets from this interface are being dropped because the low threshold has been reached, use the GWCON (Talk 5) error command and look at the Input Flow Drop counter value for the interface.

The range of values is 1 to 255. The default is both product-specific and device-specific. The low threshold should be less than the requested number of receive buffers. Specifying a value of 0 restores the autoconfigured default.

Use the GWCON (Talk 5) buffer and queue commands to show the low threshold setting.

Interface# is the number of the interface you are configuring. Low_#_of_receive_buffers is the low threshold value.

location sysLocation
Sets the physical location of an SNMP node. There is a limit of 80 characters for the sysLocation name length. This variable is for information purposes only and has no effect on device operation. It is useful for SNMP management identification of the system.

logging level #
Controls the output of messages that have not yet been converted to the ELS. (Refer to for more information about the ELS.) The logging level is recorded in the configuration. When the device is powered on or restarted, the logging level takes effect and determines message output. The default logging level is 76. Logging level 0 equates to no logging level.
Example: set logging level 76

packet-size max_packet_size_in_bytes
Establishes or changes the maximum size for global buffers and receive buffers. If you specify a value of 0 as the maximum packet size, the size of receive buffers for an interface is based on that interface's configured packet size and the packet size of global buffers are autoconfigured. If you specify a non-zero value, the configured value is used as the global buffer packet size and any interfaces that have a configured packet size that is larger than the maximum packet size will use the maximum packet size for their receive buffers. A value of 0 (for autoconfigure) is the default.
Attention:Use this command only under direct instructions from your service representative. Never use it to reduce packet size - only to increase it.

prompt user-defined-name
Adds a user-defined name as a prefix to all operator prompts, replacing the hostname.

The user-defined-name can be any combination of characters, numbers, and spaces up to 80 characters. Special characters may be used to request additional functions as described in Table 10.

Example:

set prompt
What is the new MOS prompt [y]? AnyHost 99
AnyHost 99 Config>

Table 10. Additional Functions Provided by the Set Prompt Level Command
Special Characters Function Provided by the Set Prompt Level Command
$n Displays the hostname. This is useful when you want the hostname included in the prompt. For example:
Config> set prompt
What is the new MOS prompt [y]? $n
hostname:: Config>
$t Displays the time. For example:
Config> set prompt.
What is the new MOS prompt [y]? $t
02:51:08[GMT-300] Config>
$d Displays the current date-month-year. For example:
Config> set prompt.
What is the new MOS prompt [y]? $d
26-Feb-1997 Config>
$v Displays the software VPD information in the following format: program-product-name Feature xxxx Vx Rx.x PTFx RPQx
$e Erases one character after this combination within the user-defined prompt.
$h Erases one character before this combination within the user-defined prompt.
$_ Adds a carriage return to the user-defined prompt.
$$ Displays the $.
Note:You can combine these commands. For example:
Config> set prompt
What is the new MOS prompt [y]? $n::$d
hostname::26-Feb-1997 Config>

receive-buffers interface# max#
Adjusts the number of private receive buffers for most interfaces to increase the receive performance of an interface and to reduce flow control drops when the router is forwarding many packets from a fast interface to a slow interface. The range of values is 5 to 1000. To restore the default, specify a value of 0. Not all device types allow the maximum number of receive buffers to be configured or support up to 1000 receive buffers. Use Table 11 to determine the default and maximum values for each device type. This command does not enforce the maximum values shown in Table 11. It allows you to configure a maximum value that is not supported by a device. The effect of this command is shown by the GWCON buffer command. If you configure a valid maximum value, this value appears in the Input Req column of the GWCON buffer command output. If you configure a maximum value that is not supported by the device, the GWCON buffer command shows the default number of receive buffers in the Input Req column and a GW subsystem ELS message is logged.
Note:This command is not applicable for ISDN Primary Rate Interfaces. For ISDN PRI, the number of receive buffers is fixed at 5 per B-channel, 115 for T1 and 150 for E1. When in channelized mode, the PRI gets 5 receive buffers per configured timeslot.

Table 11. Default and Maximum Settings for Interfaces
Interface Default Maximum
ATM 80* 1000
10 Mbps Ethernet 40* 1000
10/100 Mbps Ethernet 64* 1000
Serial 24 250
TKR 40* 1000
FDDI 80 80
HSSI 60* 1000
ESCON 1000 1000
PCA 1000 1000

* This is the default value for the 2216-400. For Network Utility, the default value is 1000

spare-interfaces n
Defines n, the number of spare interfaces, for this device. See Configuring Spare Interfaces for additional information.

System Retrieve

Use the system retrieve command to retrieve one or more memory image files from the installed hard drive after a serious error has occurred.

Syntax:

system
retrieve

Uses TFTP to send selected memory image files to a remote host. The system will prompt you for the remote host's IP address and file names.

If there are no dump files, you will receive the following message:

No dump files exist to retrieve

Example:

Config> system retrieve 
 
Current System Dump Settings: 
   Re-enable System Dump following the next system dump. 
   Save the first 3 (initial) dump files, then disable system dump. 
 
3 dump files currently exist. 
 
Do you want to see a summary of the dump files ? (Yes, No): [No] No 
 
Destination IP address [0.0.0.0]? 9.9.9.1 
 
Filename: core0.cmp 
Dump Date:  Tue May 05 14:38:59 1998 
 
Do you want to retrieve this file ? (Yes, No): [No] Yes 
Fully qualified destination path/file name [/tmp/dump0.cmp]? 
The memory image file is 19.3 Mb long. 
 
Proceed? [No]: Yes 
Sending memory image file by tftp 
TFTP transfer of /hd0/core0.cmp complete, size=20331888 status: OK 
tftp transfer completed successfully. 
 
Filename: core1.cmp 
Dump Date:  Wed May 06 07:53:51 1998 
 
Do you want to retrieve this file ? (Yes, No): [No] 
 
Filename: core2.cmp 
Dump Date:  Wed May 06 09:14:55 1998 
 
Do you want to retrieve this file ? (Yes, No): [No] 

System View

Use the system view command to display the current system dump settings and the status of the system dumps, including how many dump files exist. You can also display a summary of the dump files.

Syntax:

system
view

Example:

 
 
Config> system view 
 
Current System Dump Settings: 
   Re-enable System Dump following the next system dump. 
   Save the first 3 (initial) dump files, then disable system dump. 
 
Current System Dump Status: 
   System dump is currently enabled. 
   Number of existing dump files:  2 
 
Do you want to see a summary of the dump files ? (Yes, No): [No] Yes 
------------------------------------------------------ 
Filename: core0.cmp 
 
Dump Date:  Tue May 05 14:38:59 1998 
 
Fatal messages: 
  Data St. Excp Reading 0x6c6966b1 at 0x3090fca4  in thread MOSDBG (0x304d54) 
 
CMVC Build:  cc_144b 
Builder:  build 
Build Name:  LML.ld 
Retain Name:  MAS.DF1 
Product Number:  2216-MAS 
Build Date:  Wed May  6 11:47:03 1998 
 
------------------------------------------------------ 
Filename: core1.cmp 
 
Dump Date:  Wed May 06 07:53:51 1998 
 
Fatal messages: 
  Data St. Excp Reading 0x6c6966b1 at 0x3090fca4  in thread MOSDBG (0x304d54) 
 
CMVC Build:  cc_144b 
Builder:  build 
Build Name:  LML.ld 
Retain Name:  MAS.DF1 
Product Number:  2216-MAS 
Build Date:  Wed May  6 11:47:03 1998

Time

Use the time command to set the 2216 system clock and date, and to display the values on the user console. These values can then be used to time-stamp ELS messages.
Note:The 2216 has a hardware clock that maintains the date and time after device reinitialization.

Syntax:

time
host . . .

list

offset

set . . .

sync . . .

host IP_address
Sets the IP address of the RFC 868-compliant host that will be used as the time source. This is the address of a host which will respond to an empty datagram on UDP port 37 with a datagram containing the current time.

list
Displays all configured time-related parameters. This includes the current time (if set) and the source of the time (operator or IP address from which time was last received).
Example: time list
05:20:27  Wednesday December 7, 1994
Set by: operator
Time Host:  131.210.4.1
Sync Interval: 10 seconds GMT
Offset:  -300 minutes

offset minutes
Defines the time zone, in minutes, offset from GMT (Greenwich Mean Time). Note that values west of GMT are negative. For example, EST is 5 hours earlier than GMT, so the command would be time offset -300.

Valid values: -720 to 720

Default value: 0

set <year month date hour minute second>
Prompts you to set the current time. If you do not specify the entire time in the command, you are prompted for the remaining values. You can change the date as shown in the following example.
Example: time set
year [1996] 1997
month [12]?
date [6]? 7
hour [11]? 12
minute [3]?
second [2]?

sync seconds
Sets the period, in seconds, at which the device will poll the time host for the current time.

Unpatch

Use the unpatch command to restore the values of the patch variables entered with the patch command to their default values. See the patch command in "Patch" for details.

Syntax:

unpatch
variable_name
Note:You must specify the complete name of the patch variable to be restored.

Update

Use the update command to update the configuration memory when you receive a new software load.

Syntax:

update
version-of-SRAM

Follow the instructions on the release notice sent with the software. The update command is the last command that you enter when loading new software. After you enter this command, the console displays a message indicating configuration memory is being updated.

Write

Use the write command to save a configuration to the device before reloading.

Syntax:

write
 

If you fail to issue the write command and try to reload the device, you will be asked if you want to save the configuration. The configuration is saved in the next CONFIG on the hard disk in the bank you are currently using.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]